feat(calendars): add hot releases endpoint contract#848
Merged
Conversation
Adds the `/calendars/releases/hot/:start_date/:days` contract: a global-only merged feed of upcoming movies and episodes that are trending or highly anticipated, ordered by availability date. Optional `type` query narrows to a single media type; the response is a union of the movie and episode calendar entries. Bumps the package to 0.4.22.
vladjerca
force-pushed
the
feat/hot_releases_calendar
branch
from
b975177 to
6414218
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds the contract for a new global calendar endpoint:
Returns a single merged feed of upcoming movies and episodes in the window that are trending or highly anticipated, ordered by availability date.
typenarrows to one media type; omitted returns both. The response is a union of the existing movie and episode calendar entries (hotReleaseResponseSchema), so consumers discriminate by shape (movievsepisode/show).No
targetpath param: this is the global feed only, so the shared calendar params schema is reused via.omit({ target: true }).Why
Backs the "hot releases" surface, which today is assembled client-side from a releases-calendar fetch plus separate trending/anticipated fetches and an in-browser intersect. The worker now serves that server-side (trakt/trakt-workers#1181); this contract exposes it typed.
Version
Bumps
@trakt/apito 0.4.22.Notes
The 5 pre-existing
sync/HistoryRequest.test.tstype-check failures are unrelated to this change (untouched here).